This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: java.library.path problem with JVM ~Denise Minnibergobu 10.Oct.02 07:41 PM a Web browser Domino Server 6.0Windows NT
Here was the other reasons why we use JavaUserClasses :
JavaUserClasses
The variable is set to a list of directories or JAR or ZIP files that are added to the CLASSPATH at JVM startup so that classes can be found via the system loader rather than attached to the agent or applet. This allows code sharing across databases.
JavaUserClasses
If your Java agent calls another class that has native methods, you must make sure that that class is loaded via the JVM’s system loader. To ensure this, set this variable to the file name of the class file that contains the native methods. The variable's syntax is:
JavaUserClasses=<directory/filename>
By setting this variable, you override a security restriction contained in the agent class loader that does not allow classes with native methods to be loaded. This variable may be set in either or both the client and the server NOTES.INI file.